After installing SCCM 2012 SP1, one of our primary sites is intermittently experiencing the error below.  After speaking with Microsoft support, they say it is a normal error.  Our monitoring software doesn't show that the primary or remote SQL server is inaccessible at anytime.  I'm wondering if others are experiencing these type errors and if it is truly normal?

MS Engineer: I have checked the SQL Server and ran a query to find an error messages and information  for SQL and your SQL server does not have any
MS Engineer: I also consulted with few experts at my end regarding the Error Message for SQL that your getting site component status
MS Engineer: and found that the messages that you are getting there are normal

Alert details:
An unhandled exception has occurred - System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
Refer to rcmctrl.log for further details.

RCMCTRL.Log details:
ERROR: Received unhandled SQL exception, printing info and throwing it again. This will be retried in next cycle.                SMS_REPLICATION_CONFIGURATION_MONITOR            2/27/2013 6:13:21 AM    4768 (0x12A0)

ERROR: Exception message: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.]            SMS_REPLICATION_CONFIGURATION_MONITOR            2/27/2013 6:13:21 AM    4768 (0x12A0)

STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=SCCMSRV1.mydomain.org SITE=FA1 PID=2428 TID=4768 GMTDATE=Wed Feb 27 12:13:21.691 2013 ISTR0="System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)~~   " ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0   SMS_REPLICATION_CONFIGURATION_MONITOR            2/27/2013 6:13:21 AM    4768 (0x12A0)

Failed to call Configure of RCM. error = Unknown error 0x80131904         SMS_REPLICATION_CONFIGURATION_MONITOR                2/27/2013 6:13:21 AM    4768 (0x12A0)

I've never seen this on SP1 sites.

Has anyone else seen this error?  I'm hesitant on having MS premier support close this incident as normal when I continue to receive the error on a regualr basis.

Thanks!

hello tyson3264,

since about 1 week we experience the same issue. it happens every 30 minutes. when i restart the sql server all is fine again, but after some hours (usually overnight) the error reappears.

ERROR: Received unhandled SQL exception, printing info and throwing it again. 26.03.2013 07:34:59 4708 (0x1264)
ERROR: Exception message: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.] 26.03.2013 07:34:59 4708 (0x1264)
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=server.domain.com SITE=WTF PID=2268 TID=4708 GMTDATE=Tue Mar 26 06:34:59.725 2013 ISTR0="System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.~~   at System.Data.SqlClient.SqlConnection.OnError(SqlException exce" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 26.03.2013 07:34:59 4708 (0x1264)

the cpu is maxed out at 100% with sqlservr.exe.

additionally, all our secondary site links are marked with a question mark symbol from that point on:

anyone got an idea what to check? this error seems critical to me and i fear we might need to open another MS ticket......

• Edited by Robert Rostek Tuesday, March 26, 2013 8:05 AM

hello tyson3264,

since about 1 week we experience the same issue. it happens every 30 minutes. when i restart the sql server all is fine again, but after some hours (usually overnight) the error reappears.

ERROR: Received unhandled SQL exception, printing info and throwing it again. 26.03.2013 07:34:59 4708 (0x1264)
ERROR: Exception message: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.] 26.03.2013 07:34:59 4708 (0x1264)
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=server.domain.com SITE=WTF PID=2268 TID=4708 GMTDATE=Tue Mar 26 06:34:59.725 2013 ISTR0="System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.~~   at System.Data.SqlClient.SqlConnection.OnError(SqlException exce" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 26.03.2013 07:34:59 4708 (0x1264)

the cpu is maxed out at 100% with sqlservr.exe.

additionally, all our secondary site links are marked with a question mark symbol from that point on:

anyone got an idea what to check? this error seems critical to me and i fear we might need to open another MS ticket......

• Edited by Robert Rostek Tuesday, March 26, 2013 8:05 AM

hello tyson3264,

since about 1 week we experience the same issue. it happens every 30 minutes. when i restart the sql server all is fine again, but after some hours (usually overnight) the error reappears.

ERROR: Received unhandled SQL exception, printing info and throwing it again. 26.03.2013 07:34:59 4708 (0x1264)
ERROR: Exception message: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.] 26.03.2013 07:34:59 4708 (0x1264)
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=server.domain.com SITE=WTF PID=2268 TID=4708 GMTDATE=Tue Mar 26 06:34:59.725 2013 ISTR0="System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.~~   at System.Data.SqlClient.SqlConnection.OnError(SqlException exce" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 26.03.2013 07:34:59 4708 (0x1264)

the cpu is maxed out at 100% with sqlservr.exe.

additionally, all our secondary site links are marked with a question mark symbol from that point on:

anyone got an idea what to check? this error seems critical to me and i fear we might need to open another MS ticket......

• Edited by Robert Rostek Tuesday, March 26, 2013 8:05 AM

thanks for the info.

i monitored this from yesterday: the error is gone once i restart sql server, and exactly at 00:36 it appears again for the first time. 100% cpu usage from sqlservr.exe ....

what happens at midnight related to the SMS_REPLICATION_CONFIGURATION_MONITOR component?

• Edited by Robert Rostek Wednesday, March 27, 2013 7:31 AM

thanks for the info.

i monitored this from yesterday: the error is gone once i restart sql server, and exactly at 00:36 it appears again for the first time. 100% cpu usage from sqlservr.exe ....

what happens at midnight related to the SMS_REPLICATION_CONFIGURATION_MONITOR component?

• Edited by Robert Rostek Wednesday, March 27, 2013 7:31 AM

following this SQL perfmon article

http://www.mssqltips.com/sqlservertip/2454/how-to-find-out-how-much-cpu-a-sql-server-process-is-really-using/

i run these queries

SELECT spid, kpid, dbid, cpu, memusage FROM sysprocesses where kpid=1876

SELECT spid, kpid, status, cpu, memusage, open_tran, dbid FROM sysprocesses WHERE spid=180

dbcc INPUTBUFFER(180)

and gut the following result:

EventType Parameters EventInfo
RPC Event 0 CM_WTF.dbo.spDrsSummarizeSendHistory;1

what is "Summarize Send History" and why is it locking my cpu at 100% ? can anyone tell?

I can confirm we are seeing this error as well.  Here's the snippet from my rcmctrl.log.  I JUST noticed this today.  Restarted the server and the error went away. (for now at least)

ERROR: Received unhandled SQL exception, printing info and throwing it again. SMS_REPLICATION_CONFIGURATION_MONITOR 4/16/2013 11:31:42 AM 9820 (0x265C)
ERROR: Exception message: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.] SMS_REPLICATION_CONFIGURATION_MONITOR 4/16/2013 11:31:42 AM 9820 (0x265C)
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=primarysite.ourdomain.com SITE=P10 PID=14888 TID=9820 GMTDATE=Tue Apr 16 15:31:42.196 2013 ISTR0="System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.~~   at System.Data.SqlClient.SqlConnection.OnError(SqlException exce" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_REPLICATION_CONFIGURATION_MONITOR 4/16/2013 11:31:42 AM 9820 (0x265C)

The asynchronous command finished with return message: [A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 4/16/2013 11:33:51 AM 8400 (0x20D0)
The asynchronous command finished with return message: [A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 4/16/2013 11:33:52 AM 8400 (0x20D0)
The asynchronous command finished with return message: [A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 4/16/2013 11:33:52 AM 8400 (0x20D0)

We are SCCM 2012 SP1 (clean SP1 install) with SQL 2012 CU2 on Windows Server 2008 R2

Looks like it might be time for another call into Microsoft.  The error is back again this morning for us:

From the Status Message viewer:

An unhandled exception has occurred - System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exc.

Here's the info in rcmctrl.log.  I highlighted a some interesting entries..

Rcm control is waiting for file change notification or timeout after 60 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:06 AM 21692 (0x54BC)
ERROR: Received unhandled SQL exception, printing info and throwing it again. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
ERROR: Exception message: [A severe error occurred on the current command.  The results, if any, should be discarded.~~A severe error occurred on the current command.  The results, if any, should be discarded.] SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
*** [08001][26][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
*** [08001][109][Microsoft][SQL Server Native Client 11.0]Shared Memory Provider: The pipe has been ended. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
*** [08001][26][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
*** [08001][109][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection due to prelogin failure SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:15 AM 27436 (0x6B2C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_P10" requested by the login. The login failed. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_P10" requested by the login. The login failed. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
Info: Currently Site P10 is initializing Site Control Data. Can't get Master SCF from database at this time. Will try later. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=MYSERVER.MYDOMAIN.com SITE=P10 PID=17188 TID=27436 GMTDATE=Wed Apr 17 13:28:15.495 2013 ISTR0="System.Data.SqlClient.SqlException: A severe error occurred on the current command.  The results, if any, should be discarded.~~A severe error occurred on the current command.  The results, if any, should be discarded.~~   at System.Data.SqlClient.SqlConn" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 27436 (0x6B2C)
Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 21820 (0x553C)
Processing Replication Monitor SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 21820 (0x553C)
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 21692 (0x54BC)
Rcm control is waiting for file change notification or timeout after 60 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:17 AM 21692 (0x54BC)
Summarizing all replication links for monitoring UI. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:18 AM 21820 (0x553C)
The current site status: ReplicationActive. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:20 AM 21820 (0x553C)
DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:47 AM 26832 (0x68D0)
DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:52 AM 20052 (0x4E54)
Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:52 AM 20052 (0x4E54)
The asynchronous command finished with return message: [A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:53 AM 20052 (0x4E54)
The asynchronous command finished with return message: [A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:53 AM 20052 (0x4E54)
The asynchronous command finished with return message: [A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 4/17/2013 9:28:53 AM 20052 (0x4E54)

Yeah, so this error goes away for awhile if I reboot the server but for the last 3 days (since I have noticed it) it comes back.  Once its back it happens every 30 minutes according to the rcmctrl.log.  Looks like it starts at 1:30 AM, and then every 30 minutes thereafter.  Digging through now to see what happens at 1:30AM.  :-/

Yeah, so this error goes away for awhile if I reboot the server but for the last 3 days (since I have noticed it) it comes back.  Once its back it happens every 30 minutes according to the rcmctrl.log.  Looks like it starts at 1:30 AM, and then every 30 minutes thereafter.  Digging through now to see what happens at 1:30AM.  :-/

Hi William. Did you get a solution to this issue?

I'm still working with MS support on this issue as the SQL error returned last week and we are getting continuous site degraded messages.  After applying the SCCM 2012 SP1 CU1 patch, it seems to decrease the degraded errors, but did not eliminate them.  As for the SQL error, this might be due to a mis-match of table columns between two sites.  Well that is the current action plan from MS.  Below is the query MS is using to look for more details.

Select top 1000 * from vlogs where logtext like '%error%' order by logtime desc

No Luck. Checked again this morning and received the error at 3:30 AM last night, then every 30 minutes thereafter.  Haven't found any "events" yet that correlates to the timing when these errors start to appear.  Going to keep watching this thread.  Hoping tysons3264 will get some good info from Microsoft.

just reporting that we still have this popping up every night, CU1 applied but makes no difference.

waiting for a fix....

Yeah, we are at CU1 now as well.  Problem remains.  Didn't expect CU1 to fix it since its not on the known issues list but wanted to update the thread that this problem exists on both SP1 and SP1 CU1.

I'm still working with MS on the SQL exception timeout error, they have now created a sub-incident and assigned it to the SQL team for further review.

Also, we are now getting the following error when creating new client settings.  We had created new client settings after the SP1 upgrade, so this appears to be related to the CU1 patch.  We had 19 total client settings and are now down to 17, but still receive the same error.
"The maximum number of settings allowed has been reached. If you want to create a new setting, please delete an old setting and try again."
 
Others who updated to CU1 might want to check for this failure as well.

Tyson, are you getting that client settings error in the console or a log?

William, all admins are getting the error on the console of all sites when trying to create either a device or user client setting.  Error details are below.  I don't see any related component alerts that are being triggered.  MS is remotely connected now trying to find the correct log file. 

---------------------------

Configuration Manager

---------------------------

The maximum number of settings allowed has been reached. If you want to create a new setting, please delete an old setting and try again.

---------------------------

OK  

---------------------------

Hi Tyson,

We are facing exact the same problem in a hierarchy with a CAS, PSS and 6 SSS. The issue is impacting only the primary site and the according database server. There seems to be no direct relation applying SP1 but after 2 weeks thereafter this behavoir occurs. Both CAS and PSS do not share there SQL instance and operates dedicated. We are running SQL Server 2012 SP1 Standard edition.

Additional to the ERROR: Received unhandled SQL exception Timeout expired... occasionally this message pop-ups as well ERROR: A tranport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) 

Thanks for sharing the queries Robert - the SP dbo.DrssummarizeSendHistory is causing the CPU hit. We do applied CU1 as well bo we do not facing issues regarding Client- nor User settings. We are using just the default client settings.

As your last update is from late April I am wondering if you could provide us an update regarding the Microsoft PSS call? If stated this is normal behavoir that is fine to me but I would like to have an official statement, this for understanding and the fact these messages can indicated as false positives and therefore safely be ignored. Consider fineuning monitoring (Component Status/Management Pack)

T

Any update from MS on this issue?  I am also seeing the same SQL exception timeout errors in my environment post SP1 upgrade.  While they happen sporadically through the early morning hours, when they do trigger, the are occurring every 30 minutes and then eventually clear up.

In regards to the SQL exception error, I am still working with MS on this issue. The reason it's taking so long as sometimes we go 2-3 weeks without receiving the error message. The error just returned last week and I have uploaded the initial trace files to MS for review, but have not heard back on any findings. I have a more detailed trace running now to capture more system information as the error occurs.

Update on Client Settings issue: This is resolved. Somehow the CU1 patch caused the priority value for the majority of our Client Settings to decrease from a 1-20 value to a 4990 - 5000+ value. We are able to create new client settings again after I created a PowerShell loop script to increase the priority of each to the 1-20 range.

Thanks for tour Quick reply. Please could you provide some more background regarding your SQL configuration? Is your instance on high CPU pressure? This identify it is performance, network, SCCM or SQL related

Regards,.

It happens on both our CAS and one of our primary sites.  Both are physical servers, CAS (16 core/64 GB - Local SQL) and primary (12 core/32 GB - Remote SQL).  I've never seen these servers being capped on CPU or memory.  The errors only started after the SP1 upgrade.
SQL on CAS is set to use minimum 24 GB and maximum 50 GB RAM.

Here are some CPU, RAM, and network performance counters from last night when the error occurred around 12:30 AM.

https://skydrive.live.com/redir?resid=CDC126E024B842DA!130&authkey=!AP5PixwD1EvZvxY
https://skydrive.live.com/redir?resid=CDC126E024B842DA!131&authkey=!ACM3mvUK2JoKM1U

Yeah, I can confirm this error did not start appearing until SP1.  Our primary is 16 core with 64GB of memory, SQL is local and memory is Min 8GB, Max 32GB.  We currently only have about 400 of our 3000 clients reporting to it.  Not an available resource issue on our end.

Hi All,

Just enabled verbose logging (blog) Monitor component which provides some more details on the SqlException. I've actually no clue regarding SqlException.

ERROR: Received unhandled SQL exception, printing info and throwing it again. SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
SqlException number: [-2] SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
ERROR: Exception message: [Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.] SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
Exception stack trace: [   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)~~   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)~~   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)~~   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)~~   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)~~   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)~~   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)~~   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()~~   at Microsoft.ConfigurationManager.ServerComponents.DatabaseOperation.ExecuteStoredProcedure(String storedProcedureName, Int32 timeout, List`1 commandParameters)~~   at Microsoft.ConfigurationManager.ReplicationConfigurationAndMonitoring.ReplicationConfigureAndMonitor.TaskSummarizeSendHistory(Object threadContext)] SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
STATMSG: ID=7832 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_REPLICATION_CONFIGURATION_MONITOR" SYS=<SCCM Server> SITE=E01 PID=1932 TID=4552 GMTDATE=wo mei 29 13:01:19.573 2013 ISTR0="System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.~~The statement has been terminated.~~   at System.Data.SqlClient.SqlConnection.OnError(SqlException exce" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
Releasing sqlConnection System.Data.SqlClient.SqlConnection SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
Found existing sqlConnection to <DATABASESERVER> SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)
Releasing sqlConnection System.Data.SqlClient.SqlConnection SMS_REPLICATION_CONFIGURATION_MONITOR 29-5-2013 15:01:19 4552 (0x11C8)

Looking to the Database Replication monitoring workspace all link states having a status Link Unknown. Performing a refresh or RLA action does not change the status to active.

Latest update... The SQL Connection team looked over the first set of trace files and was unable to determine any 'connection' issues.  I was able to capture PSSDIAG traces this morning for two of the errors and have submitted them to MS so the SQL Performance team can review them.

Thanks for keeping us posted..

Error continues, Microsoft isstill unable to determine any issues from the SQL traces.  We now have network monitor 3.4 and snac bid traces running.

Thanks for updating the thread. It seems we have a fixed pattern now. Every day between 00:30AM and 02:30 AM. Site Server backup task is scheduled between 03:00AM and 05:00, SQL backup at 00:00AM. Remaining actions that could potentially affects this behaviour are the site maintenance jobs which are by default scheduled between 00:00 and 05:00. To exclude any possible relationship we've rescheduled the maintenance jobs at a later time. Keeps you posted whether this effect on the time-outs or the cause is external (network, hypervisor, stor

The SQL time-outs having an arguable relation with the Delete Aged Replication Summary Data or Delete Aged Replication Tracking Data site maintenance jobs. When changing the schedules the SQL time-outs moved along with the newly set schedules.

• Edited by Ronny de Jong Monday, June 10, 2013 7:25 AM

The SQL time-outs having an arguable relation with the Delete Aged Replication Summary Data or Delete Aged Replication Tracking Data site maintenance jobs. When changing the schedules the SQL time-outs moved along with the newly set schedules.

• Edited by Ronny de JongMVP Monday, June 10, 2013 7:25 AM

Hi Robert,

This is (almost) for sure caused by Delete Aged Replication Summary Data or Delete Aged Replication Tracking Data site maintainance task(s). Just playing around with the schedules and you'll see the SQL time-outs moved along with the newly set site maintainance schedules.

The SQL time-outs having an arguable relation with the Delete Aged Replication Summary Data or Delete Aged Replication Tracking Data site maintenance jobs. When changing the schedules the SQL time-outs moved along with the newly set schedules.

• Edited by Ronny de Jong Monday, June 10, 2013 7:25 AM

Hey guys, this feel off my radar until today when we noticed OpsMgr alerts showing the issue had returned.  Did anyone ever get a resolution on this?

Thanks!

Hi tyson3264,

Has there been an update on this. Even with CU2 we are still have the above issues.

Cheers,

Same here. On CU2 and same issue is occurring. 

For anyone else still with the issue. We got it sorted on our end. In the end it wasn't SCCM that caused the issue it purely helped with the problem due to how many connections it makes to the SQL server.

Here is what we did. It appears there were two issues.

1. Boost SQL Performance was ticked. This is now un-ticked. Reference
2. Also client connections/TCPIP (for 64 bit) was only enabled, not Right click, properties, Enabled, Enabled, Enabled, Enabled, Enabled, Enabled, Enabled, Enabled, Enabled Again because you can never have enough Enableds) Reference

Hope this can help others.

Thanks for the reply Zac.

Just checked and Boost SQL Performance was not enabled on our server.

Would like to hear from others as well on whether enabling TCP/IP as referenced above in SQL Server Configuration Manager worked for them as well and if there were any downstream implications.  

The TCP/IP enabling was the main cause of our issue. We saw a very slight improvement when we disabled the Boot SQL Performance option but the enabling of the other connections was the primary factor for us.

As I understand it you enable TCP/IP at a higher level (Which it was for us) but then you actually have to go into the settings and then enable the specific connections that fall within the TCP/IP settings that you want to enable.

I have enabled the TCP/IP settings today and will monitor for the return of the error.  Zac, can you confirm whether or not your error returned now that its been a few weeks since enabling?

Thanks!

Well unfortunately I can confirm that the error persist for me after enabling the TCP/IP settings per above. :-/

*We are on SCCM 2012 SP1 CU3.

Sorry it didnt work for you. I guess just double check that you enabled the TCP/IP settings for the correct IP Range as there are heaps listed.

We did also reboot the server after the change.

We are also on SP1 CU3. In saying that though for us atleast it wasnt SCCM causing the issue. The issue was with SQL it was simply because SCCM makes so many calls to SQL it made the issue more prevalent.

Hey Zac, can you expand on what you mean by the IP Ranges?  The area where I changed "Enabled" to True was under the SQL Server Network Configuration>Protocols for MSSQLSERVER, then the IP Addresses tab.  This only lists the multiple IP addresses available on my server, not IP Address ranges?  Just want to ensure I didn't miss something.

Thanks!

I am also experiencing similar issues with my Primary site server's dedicated SQL 2012 instance. I am running SCCM 2012 RC2 and my SQL Server installation is 11.0.3381.0. I have the same version on my CA however it never runs very hot so this issue has perplexed me. I have tried a few different approaches but nothing has improved the performance and now it seems that every couple of days the server will end up jamming itself up with queries and the processor time will stay in the up 90% range. If I restart the service it will stay low to mid range for a while and things will seem to work fine but eventually it will rise up again and then other SCCM services are impacted (i.e. collection evaluation, package distribution, etc.). I have discussed adding more cores to the VM that hosts this server but I am convinced that the issue is of software configuration and that throwing more cores at the problem doesn't actually address the root.

I did take Zac's suggestion and looked at the "Boots SQL Server priority" option within the Server Properties -> Processors section and it was not selected:

I also went into the SQL Server Configuration Manager and found the TCP/IP Protocol for my SQL instance and enabled TCP/IP for all of the connections available which includes local host 127.0.0.1, the IPv6 and the individual ports specified for use by the SQL server.

After I checked and enabled the ports I restarted the SQL server and it doesn't appear to have impacted the performance in a dramatic way. The %Processor Time% starts at around 50% and I expect that I will see it rise over the next few hours back up to the mid-90% range.

As a side note I have taken a look at the diagnostic queries mention here by Derek Deiter as part of SQL 2008 performance troubleshooting and they do provide some insight into what queries are consuming the CPU. The leading query is: spDrsSummarizeSendHistory which is how I actually landed in this Technet forum. I was looking at the Software Update Summarization process yesterday after reading several threads relating to that. I found that the process was set to run every hour and many people suggested turning that down; however there wasn't a consensus as to what the frequency should be. I decided to set my summarization to 6 hours (though that didn't seem to make a big difference in the SQL issue).

If anyone has any further insight into this issue I would definitely appreciate it and if I can provide more detail regarding my configuration, please let me know.

Thanks,

CB

ConfigMgr "RC2" or "R2"? Huge difference.

Hello everyone,

We are running SCCM 2012 R2 and we get the exact same error every night - every half hour for 8 hours.  Has anyone ever received closure on it? 

Hi All

Has anyone got to the bottom of this as I've tried everything in the article but the errors still appear..

Thanks

Hello,

Any solution to fix this issue? I'm facing the same issue in my environment having sccm 2012 R2 CU1. 

Thanks.

Any solutions?  I'm starting to see the same errors, mostly in the early mornings every 1 to 2 hours.  

SCCM 2012 R2 CU3 

We are seeing similar errors mostly early morning after every 30 mins. Did anyone managed to fix this out?

Please contact Microsoft support - otherwise they are not aware of that issue and it will never be fixed.